home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 2001 May
/
SGI IRIX Base Documentation 2001 May.iso
/
usr
/
relnotes
/
websupport_eoe
/
ch2.z
/
ch2
Wrap
Text File
|
2001-04-17
|
7KB
|
263 lines
- 1 -
2. _I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n
This chapter lists supplemental information to the _I_R_I_S
_S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e. The information listed here is
product- and release-specific; use it with the Installation
Guide to install this product.
2.1 _W_e_b_S_u_p_p_o_r_t__S_u_b_s_y_s_t_e_m_s
WebSupport includes these subsystems:
_w_e_b_s_u_p_p_o_r_t__e_o_e._s_w._l_i_b Runtime environment for o32
_w_e_b_s_u_p_p_o_r_t__e_o_e._s_w_3_2._l_i_b Runtime environment for n32
_w_e_b_s_u_p_p_o_r_t__e_o_e._s_w_6_4._l_i_b Runtime environment for 64
2.2 _W_e_b_S_u_p_p_o_r_t__S_u_b_s_y_s_t_e_m__D_i_s_k__S_p_a_c_e__R_e_q_u_i_r_e_m_e_n_t_s
This section lists the subsystems (and their sizes) of
WebSupport.
If you are installing this product for the first time, the
subsystems marked ``default'' are the ones that are
installed if you use the ``go'' menu item. To install a
different set of subsystems, use the ``install,''
``remove,'' ``keep,'' and ``step'' commands in _i_n_s_t to
customize the list of subsystems to be installed, then
select the ``go'' menu item.
Note: The listed subsystem sizes are approximate. Refer to
the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information
on finding exact sizes.
Subsystem Name Subsystem Size
(512-byte blocks)
_w_e_b_s_u_p_p_o_r_t__e_o_e._s_w._l_i_b (default) 688
_w_e_b_s_u_p_p_o_r_t__e_o_e._s_w_3_2._l_i_b (default) 1108
_w_e_b_s_u_p_p_o_r_t__e_o_e._s_w_6_4._d_e_v (default) 1384
2.3 _I_n_s_t_a_l_l_a_t_i_o_n__M_e_t_h_o_d
All of the subsystems for WebSupport can be installed using
IRIX. You do not need to use the miniroot. Refer to the
_I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for complete installation
instructions.
- 2 -
2.4 _C_o_m_p_a_t_i_b_i_l_i_t_y
This release of WebSupport is API compatible with previous
releases.
2.5 _C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s
This release uses the following configuration files:
2.5.1 _S_y_s_t_e_m__M_a_i_l_c_a_p__F_i_l_e_s
1. /var/netscape/communicator/mailcap
2. /usr/local/lib/netscape/mailcap
3. /usr/lib/internal/mailcap.wio
2.5.2 _U_s_e_r__M_a_i_l_c_a_p__F_i_l_e_s
1. $HOME/.netscape/.mailcap
2. $HOME/.mailcap
2.5.3 _S_y_s_t_e_m__M_i_m_e__T_y_p_e__F_i_l_e_s
1. /var/netscape/communicator/mime.types.full
2. /usr/local/lib/netscape/mime.types.full
3. /usr/lib/internal/mime.types.wio
2.5.4 _U_s_e_r__M_i_m_e__T_y_p_e__F_i_l_e_s
1. $HOME/.netscape/.mime.types
2. $HOME/.mime.types
2.5.5 _W_e_b_s_u_p_p_o_r_t__O_p_e_r_a_t_i_o_n_a_l__F_i_l_e_s
1. $WAPPLRESDIR/webdefaults
2. /etc/webdefaults
3. $WDEFAULTS
4. $HOME/.web/.webdefaults
2.5.6 _N_e_t_s_c_a_p_e__C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s
1. $HOME/.netscape/preferences.js
- 3 -
2. $HOME/.netscape/preferences
2.5.7 _S_O_C_K_S__C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s
1. /etc/socks.conf
The above files are consulted, in order, to load resource
information for the libraries. This information consists of
SOCKS gateways, cache sizes, etc.
Here is a brief overview of the algorithm for loading
information from these files into a running websupport
instance. See the documentation for a detailed description
of the configuration files. At least one of the files from
the "Websupport Operational Files" or "Netscape
Configuration Files" must be present for websupport to
operate correctly.
"System Mailcap Files" are the first thing to be loaded.
Mailcap files dictate what a browser should do with a given
content type. For example, gif images should be shown with
imgworks. The first existing file from the list of System
Mailcap files is used. Then the first file from the list of
User Mailcap files is used. Entries in the User Mailcap
file take precedence over those in the System Mailcap file.
"Mime Type Files" are loaded in a similar fashion as the
Mailcap Files. Mime Type dictate what kinds of file
extensions are used for each content type.
"Websupport Operational Files" are loaded after the Mailcap
and Mime Type files. Entries in the Websupport Operational
Files configure important things for the library such as
network proxies, disk cache size, and disk cache location.
The first existing file from the list of Websupport
Operational Files is used.
Following the Websupport Operational Files, the first file
from the list of "Netscape Configuration Files" is used to
load any entries that need to be filled in after all the
other files have been loaded. It's sort of a fallback
mechanism if no Websupport Operational configuration files
have been installed. For example, websupport must know the
name of the socks or proxy server in order to get outside of
a firewall, and if netscape knows how to do this, websupport
will get that information from the netscape configuration
files.
The last kind of file loaded is the Socks Configuration
File. This file, if present, can be used to override low
lever socks protocol options. It's presence of this file is
- 4 -
not necessary for correct websupport operation.